docs(cli): clarify dev env-file propagation - #4473
Conversation
🦋 Changeset detectedLatest commit: 0cbf447 The changes in this PR will be included in the next version bump. This PR includes changesets to release 27 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Hi @RealBhupesh, thanks for your interest in contributing! This project requires that pull request authors are vouched, and you are not in the list of vouched users. This PR will be closed automatically. See https://github.com/triggerdotdev/trigger.dev/blob/main/CONTRIBUTING.md for more details. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
WalkthroughUpdated the ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
--env-filedocumentation for local task processes.trigger dev --helpto describe the same behavior.trigger.devpatch changeset.Root cause
The implementation already passes local
dev --env-filevalues into task processes, but the docs and CLI help incorrectly said they only affected the CLI process.Validation
Please keep this PR in draft until vouching and CI review are complete.
fixes #4425